Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Log web socket errors #139

Merged
merged 1 commit into from
Mar 7, 2019
Merged

Log web socket errors #139

merged 1 commit into from
Mar 7, 2019

Conversation

jmattheis
Copy link
Member

Adds logging like this:

[GIN] 2019/03/06 - 20:28:19 | 400 |     211.498µs |      172.18.0.1 | GET      /stream?token=CRO8zhuUfIyn2hE
Error #01: websocket: the client is not using the websocket protocol: 'upgrade' token not found in 'Connection' header

@codecov
Copy link

codecov bot commented Mar 6, 2019

Codecov Report

Merging #139 into master will not change coverage.
The diff coverage is 100%.

Impacted file tree graph

@@          Coverage Diff          @@
##           master   #139   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files          39     39           
  Lines        1415   1416    +1     
=====================================
+ Hits         1415   1416    +1
Impacted Files Coverage Δ
api/stream/stream.go 100% <100%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4814fe8...724f9df. Read the comment docs.

@jmattheis jmattheis merged commit 5c5965f into master Mar 7, 2019
@jmattheis jmattheis deleted the ws-errors branch March 7, 2019 17:29
@jmattheis jmattheis added this to the v2.0.2 milestone Mar 10, 2019
GAS85 added a commit to GAS85/website that referenced this pull request Jun 5, 2020
This config causing Error as per gotify/server#139, additional config from gotify/server#23 needed.

From: https://stackoverflow.com/questions/53939609/apache-websocket-connectionupgrade-replaced-by-keep-alive
"Apache does not understand websockets in one sense (i.e. when it is talking to itself). As a result, you need to use mod_rewrite and set the protocol to ws:// in order to forward websockets upstream (it seems that no amount of setting headers will help you here)."
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants